@jt-nti any updates？

@Varorbc unfortunately I'm recovering from Covid at the moment so it will probably take me a bit to get back to this.

Hyperledger has reserved the prefix on NuGet, which is good, but it would help if anyone familiar with publishing packages there could suggest what a "good" C# protobuf package would look like.

@jt-nti I'm very sorry to bother you, and I wish you a speedy recovery.

Perhaps you can send a preview package first, and I will give you some suggestions.

@jt-nti Hello, sorry to bother you again.Any Update?

@Varorbc hi, sorry I haven't had a chance to get back to it so far. I'll try and post something on discord to see if anyone with C#/nuget experience can suggest what needs doing next.

@jt-nti I want to know what is hindering this matter?

@Varorbc it was just a bit of a proof of concept- I think it would be a nice addition but I'm not a C# developer so I have no idea what a good example of this kind of thing should look like. It would also need to be approved and merged by one of the maintainers. The good news is that the Hyperledger prefix has now been reserved in nuget so with a bit more help with credentials etc. it should be possible to publish a package.

@Varorbc getting #228 and #229 merged in the mean time would be good though if possible. It think there was just the C# naming conventions to sort out for SmartBft etc.
https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/capitalization-conventions?redirectedfrom=MSDN